Looking at the tests this should pass. So I'm not seeing what the issue is. Nautobot has a dependency of python = ">=3.8,<3.12" in the next branch. I don't see anywhere else where the tests would be getting Nautobot 2.0 from.

2.0.0b1 didn't support python 3.11 yet. That was a more recent change. You might need to wait until b3 or rc1 before making this update.

@glennmatthews my latest dev host is Python3.11. In order to get to the poetry shell I need to be able to install. I can always move back to the NTC machine though as well, but this should catch things up.

@jvanderaa do we need to do anything with this, or can it wait until a release of 2.0 comes out support Python 3.11? If you have Python 3.9 or 3.10 installed on your system then I think you can use them with something like the following:

poetry env use python3.9

I just am unable to develop on my development workstation (Debian 12) until then. It's a personal preference thing, so I can move to developing elsewhere.

But the real process is that we should not rely on invoke in a virtual environment and that should be moved to using system python. This is a thing today with Python3.11 that will go away, but then when 3.12 and 3.13 come out it will be the same. We should migrate away from using invoke in virtual environments.

And this is fine while we have this in private. But what about when it is open source. Those that have only one dev workstation and it is modern, then we are preventing them from helping.